home *** CD-ROM | disk | FTP | other *** search
- Path: news.netins.net!trg1
- From: hhowe@trgnet.com (Harold Howe)
- Newsgroups: comp.lang.c++
- Subject: Re: Is this a memory leak?
- Date: Fri, 05 Apr 96 15:28:03 GMT
- Organization: Technology Resource Group
- Message-ID: <4k3hfn$8p6@insosf1.netins.net>
- References: <4jv214$gv7@insosf1.netins.net> <4k0c2i$h6e@werple.net.au>
- NNTP-Posting-Host: desm-21-10.dialup.netins.net
- X-Newsreader: News Xpress Version 1.0 Beta #3
-
- In article <4k0c2i$h6e@werple.net.au>,
- davidw@werple.net.au (David White) wrote:
-
- >The BuriedClass object is not deleted. Zeroing the pointer does nothing
- >but zero the pointer, which prevents the BuriedClass object from being
- >deleted. Maybe 'shutDown' is intended to be called if responsibility for
- >the BuriedClass object is moved to something else, which will delete it,
- >or maybe it's a safety measure, to be used if some sort of free store
- >corruption is detected.
- >
- >David White
- >davidw@werple.mira.net.au
-
- I think that in my case, someone else does indeed do the actual deleting of
- the memory. After searching through the library, it appears that other
- pointers are still pointing to the memory and they are the ones that actually
- get deleted. Thanks for the tip,
-
- Harold Howe
- hhowe@trgnet.com
-